Vlocity Facts #14 | Integration Procedure Properties

Integration Procedure runs in synchronous or asynchronous mode ?

By Default it will run in Synchronous mode.

To make Integration Procedure run in Asynchronous mode, call Integration Procedures using these settings from omniscript:

Use Future — Use when the calling OmniScript or Integration Procedure doesn't need a response and completion time is not critical. [Specifies that the Integration Procedure runs asynchronously, as a Salesforce future method, which can return no data to the calling OmniScript.]

Invoke Mode: Non-Blocking :The Action runs asynchronously, and the response applies to the UI. Pre and Post DataRaptor transform and large attachments are not supported.

Invoke Mode: Fire and Forget :The Action runs asynchronously with no callback to the UI. Pre and Post DataRaptor transforms, and large attachments are not supported. A response still appears in the debug console but does not apply to the Data JSON.
==============================================================================================
Chainable and queueable

By default, all the actions in an Integration Procedure run in a single transaction.

Chainable (and queueable) are used in Integration procedure to avoid hitting governor limits on an Integration procedure. One integration procedure is considered as one transaction, and when you have long running integration procedures, you have the risk of hitting one or transaction governor limits.

When chaining is enabled, if an Integration Procedure exceeds a governor limit, its interim results are saved and it is continued in a new transaction.

You can also enable a chainable IP to be queueable, which runs in Async mode, which have higher governor limits.

Chainable - Synchronous Apex Execution eg, limits of soql queries is 100
Queueable - Asynchronous Apex Execution eg, limits of soql queries is 200



Comments

Post a Comment

Popular posts from this blog

Vlocity Facts #01 | OmniStudio DataRaptors

DataRaptor is a mapping tool that  you can use to read, transform, and write Salesforce data. For Example. In each interaction with a digital customer  or business process, the system needs to extract the data in order to display it. If the user modifies this data or enters new data, they also need to be saved. This is where we use OmniStudio DataRaptors.  Where to use DataRaptors? Retrieving Data:   OmniScript calls  DataRaptor Extract (via the integration procedure) to read the data from Salesforce. For example, OmniScript editing an account should display data such as account name, phone number, website, and so on. Manipulating data: OmniScript captures modified and new data based on user input. For example, an agent changes the  phone number of an account. Save Data:   OmniScript calls DataRaptor Load (via the integration procedure) to write the data back to Salesforce. For example, the updated account phone number is saved back to the Account rec...
Read more

Vlocity Facts #34 || Getting the details from the URL in a FlexCard and an Omniscript

Image
 1.The parameters in the URL must be in the format c__Node, followed by their values, in order to extract the parameters from the URL. For example: If you need to show different layout or different set of actions for community users and salesforces users you can pass different parameters in URL. For Community Portal Pass Community or any other reference value in ' c__Type '. https://salesforce.lightning.force.com/lightning/cmp/ omnistudio__vlocityLWCOmniWrapper?c__target=c%3ApHXTestFlexCard&c__tabIcon=custom%3Acustom18& c__Type =Community  For Salesforce Users Pass Salesforce or any other reference value in ' c__Type '. https://salesforce.lightning.force.com/lightning/cmp/ omnistudio__vlocityLWCOmniWrapper?c__target=c%3ApHXTestFlexCard&c__tabIcon=custom%3Acustom18& c__Type =Salesforce  2. We can get the value as {Params.c__Parameter} from the FlexCard and we can execute different actions based on the input. 3. From the omniscript,  we can retrieve ...
Read more

Vlocity Facts #44 || Communication between Omniscript and Flexcard [Pub/Sub]

Image
Flexcards have the ability to trigger and listen to two kinds of events: Custom and Pubsub events . Custom Events: Facilitate the transmission of information between a child and its parent. This can occur between a child Flexcard and its parent Flexcard, or between an element and the Flexcard to which it belongs. Pubsub Events: Allows communication between two separate components. This could occur between two separate Flexcards on the same Lightning page, known as sibling Flexcards, or between a Flexcard and an Omniscript.  In this post I will discuss about Pub/Sub event. Consider we have omniscript and flexcard individually on home page when an update happens we need to show those details in flexcard. To achieve this we can use pub/sub event. Step 1: Create a omniscript according to your requirement. I'm trying to create Contact record by using Step element and data raptor post action. Now to trigger the flexcard we need to configure the messaging frame work when an update happen...
Read more